fix: validate Core Metadata 2.5 releases - #60

Summary

• Raise the workspace release-validator floor from twine>=6.0.0 to twine>=7.0.0.
• Refresh uv.lock from Twine 6.2.0 to 7.0.0.

Context

The corrected data-designer-retrieval-sdg/v0.2.0 publication passed its isolated Python 3.10 package suite, including the clean-provider regression fixed in #59, and built both distributions. It then stopped at twine check:

InvalidDistribution: Invalid distribution metadata: '2.5' is not a valid metadata version

The current build backend emits Core Metadata 2.5. The release workflow uses the workspace lock, which selected Twine 6.2.0; that version rejects Metadata-Version 2.5. Twine 7.0.0 accepts the same wheel and source distribution.

The failed release stopped before the package-asset and package-index steps. The GitHub release and tag were removed again after confirming that no 0.2.0 assets were uploaded and packages.json still advertises 0.1.0.

This change affects release tooling only. The retrieval SDG 0.2.0 package source and artifact contents are unchanged.

Validation

• Python 3.10 resolves Twine 7.0.0 from the updated workspace lock.
• Twine 7.0.0 validates both data_designer_retrieval_sdg-0.2.0 wheel and sdist.
• uv lock --check
• Ruff lint and formatting checks
• Release-tooling suite: 156 passed

Failed publication run: https://github.com/NVIDIA-NeMo/DataDesignerPlugins/actions/runs/31626299951